Let's face it, REST APIs can be problematic, and hypermedia hasn't quite proven to be the answer we've looked for. GraphQL has quickly become more popular offering a solution to the problems REST created - but opens back up the very problems REST was created to avoid (remember SOAP?). But what if there was a way to take the best of both: enter API chains. In this session we'll take a look at the pros and cons of REST, GraphQL, and a new specification and library for chaining numerous resource calls into a single HTTP request.

Software Engineering can be extremely difficult and maddening. But it doesn't have to be. We will explore leveraging various principles to make Software Engineering fun again. We'll make a case for "Better Code" fueling "Faster Development".

Toward building our case, we will explore 5 areas:

* Bad Code vs Agility - What it means to be "Agile" and the impact of Bad Code on Agility.
* Better Code: Enablers - Enabling Concepts for Better Code such as TDD, Clean Code and Patterns, with an eye toward adapting them to various programming paradigms such as Functional and OOP.
* Empowering OOP - If OOP is to be chosen as a paradigm, we'll explore what it means to play to the strengths of this paradigm.
* Web Application Architectures: When building Web Applications, we'll explore various architectures that may hinder or promote a sustainable business fueled by better code.
* TDD: Better Fuels Faster - Leveraging preceding topics, we'll put it all together in describing a workflow leveraging test-driven development for shipping better products ... faster, and having fun doing it.

The end of this talk will showcase code examples of a real-world Kata for building the service layer of a "Ride Hailing Application". It will also link to recorded Kata videos, as well as a "clean slate" branch in my git repository to follow along.

Having made this case, we'll conclude with the positive impact this workflow will have on a team's ability to ship new products and new features at a sustained pace, with high levels of predictability.

While PHP, Symfony and Doctrine are used for code examples, concepts in this talk are applicable to all PHP frameworks and environments, as well as other programming languages such as Java, PHP and C#.

Whether you're just starting out or an expert PHP developer, you've probably heard the dreaded line, "Works on my machine." Docker is quickly taking hold as the answer to this problem by making virtualization faster and more flexible than ever before.

In this walk-through, we'll take a step-by-step look at exactly how to set up a PHP application using Docker. Along the way we'll explore how Docker works, why containers are an improvement over virtual machines, and how this setup can eliminate differences between local and production environments.

No no, not country flags, feature flags! Feature flags are a powerful technique that allows teams to modify a system's behaviour without changing code. They can be used several reasons - canary releases and A/B testing to name a few.

This talk will show you how you're already using feature flags in your application without realising it. Next, we'll take a look at some of the best tooling out there to help you take feature flags to the next level. Finally, we'll cover strategies for removing feature flags before they become technical debt that you have to manage.

Even legacy code should have test coverage.
Finding the right places to put those tests, however is really hard. How do you add support unit tests when most of your code is tightly coupled?

We'll discuss a number of strategies to find seams in your existing legacy code, which libraries make this easier and help us test more and deeper into our legacy codebases.
We also will cover valuable metrics to measure for progress, how we should approach the issue of continually improving our tests.

By the end of this talk the audience should have a better understanding of what a seam is, how to leverage them to test code, how to use mocking libraries and runtime replacement to help get better test coverage.
Most importantly we'll all walk away feeling like we can tackle refactoring and new features with confidence.

Have you ever wondered how super globals get initialized or been curious what happens before your code is turned into an http response? Have you ever wanted to add a new feature to PHP that you could deploy across all the applications hosted on a server? 20k Lines Under the C dives deep into the source of the PHP runtime, extension APIs, and parts that make it translate your code into web pages. We'll begin by looking at how web servers provide PHP the request information. We'll follow the startup process making stops along the way pointing out the internal structure and key parts during execution where various data is initialized and processed. Through this journey we'll learn about some of the special data types that PHP exposes and the APIs used to interact with them. Finally we'll explore the the different types of PHP integrations and explore how to insert hooks into just about everything providing ways to inspect and change the behavior.

In this talk, I'll convince you that your parents were wrong & procrastination is actually a best practice. I'll discuss: what caching is, what queuing is, why you (probably) don't need live data, why you should push everything off until later & how we can get our lazy on with Redis.

This unconference session will be an attendee-driven community discusion for anyone interested in PHP development.

Remember when setting up an auth system was easy? Me neither. From the signup form, the login form, password reset form, and all the validation in between it can easily take weeks if not months to get something basic up and running. Then you have to deal with all the security considerations. No thanks. During this presentation, the attendees will be introduced to OpenID and OAuth. They will learn how to leverage these technologies to create secure applications, but most importantly, they will learn why and how to delegate authorization and authentication so they can focus on their real work and forget about all that security stuff.